-
Notifications
You must be signed in to change notification settings - Fork 640
dataconnect: fix generation of invalid timestamp values in internal test utilities #6689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dataconnect: fix generation of invalid timestamp values in internal test utilities #6689
Conversation
…e number of proper digits is 1
Release note changesNo release note changes were detected. If you made changes that should be |
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Coverage Report 1Affected ProductsNo changes between base commit (2d1905e) and merge commit (fb28713).Test Logs |
Test Results 64 files + 56 64 suites +56 1m 13s ⏱️ +54s Results for commit 96bd96d. ± Comparison against base commit f80ba89. This pull request removes 22 and adds 542 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Size Report 1Affected ProductsNo changes between base commit (2d1905e) and merge commit (fb28713).Test Logs |
Changelog entry should be picked up for the next release
If missing, they'll default to empty.
There were some issues when generating Timestamp values for testing. The first was some bad math when generating nanosecond values, where values exceeding the maximum value of 999,999,999 were being generated. The second was a boundary case where the time zone offset would push the second/nanosecond value above the maximum value or below the minimum value. This PR fixes both of those.